Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6667222409ee69fd515598d2e1f2f1667de8d83de49cf32557b7f5fe1fded956

Tx prefix hash: f21eb771c97dd7f27ecf93bec94ee7a0c77a3587cc83c6f8d109a8084750238b
Tx public key: dac6e36e94dc768613c7cfe7290e47831cd8a8a1849c6d0caf20cf63d5164791
Timestamp: 1706077356 Timestamp [UCT]: 2024-01-24 06:22:36 Age [y:d:h:m:s]: 01:101:03:13:18
Block: 942105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333391 RingCT/type: yes/0
Extra: 01dac6e36e94dc768613c7cfe7290e47831cd8a8a1849c6d0caf20cf63d51647910211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a9431743c27c74f7fb39a357b5a45466ff5e4088caa64c29dd48c11181de5b5 0.600000000000 1400271 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 942115, "vin": [ { "gen": { "height": 942105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a9431743c27c74f7fb39a357b5a45466ff5e4088caa64c29dd48c11181de5b5" } } ], "extra": [ 1, 218, 198, 227, 110, 148, 220, 118, 134, 19, 199, 207, 231, 41, 14, 71, 131, 28, 216, 168, 161, 132, 156, 109, 12, 175, 32, 207, 99, 213, 22, 71, 145, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8