Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21cf745dc0d3680ffbd43c30deb586b7ed74fb50c8686485eaeae26d82cc4ea9

Tx prefix hash: e6e93a03e3704c1afe12553ee69bbf1128180347cdef3fd77294eec10c5aeea5
Tx public key: baeb71b81073194ea6f11fa0f84f54b27d41389103909abcb16f0108efc6a1d4
Timestamp: 1703649117 Timestamp [UCT]: 2023-12-27 03:51:57 Age [y:d:h:m:s]: 01:064:12:16:42
Block: 922001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307190 RingCT/type: yes/0
Extra: 01baeb71b81073194ea6f11fa0f84f54b27d41389103909abcb16f0108efc6a1d40211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0461912c4e3ae7f03dddf26459dc3b12174cb2d14b3cae922cd0f91eea4b7610 0.600000000000 1379695 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": 922011, "vin": [ { "gen": { "height": 922001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0461912c4e3ae7f03dddf26459dc3b12174cb2d14b3cae922cd0f91eea4b7610" } } ], "extra": [ 1, 186, 235, 113, 184, 16, 115, 25, 78, 166, 241, 31, 160, 248, 79, 84, 178, 125, 65, 56, 145, 3, 144, 154, 188, 177, 111, 1, 8, 239, 198, 161, 212, 2, 17, 0, 0, 0, 2, 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