Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daf4f6d4d50f06ad15e4a19ad109307b338e9307c9923af295410bbf8ad9a31c

Tx prefix hash: ff8441c73264f6483d3fabb5e02ec3ce438663461e67a4ec9bd5a671fd771cee
Tx public key: 7ada0f919be0af7fe2bed4893eb0caa55b8df97963114c2586f72cbb6b57557a
Timestamp: 1713461881 Timestamp [UCT]: 2024-04-18 17:38:01 Age [y:d:h:m:s]: 00:290:18:07:13
Block: 1003335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207843 RingCT/type: yes/0
Extra: 017ada0f919be0af7fe2bed4893eb0caa55b8df97963114c2586f72cbb6b57557a02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 290f733a6b4d470f1d9d78a2394b4a2b1741bb70ddb98648d057ad503e94327b 0.600000000000 1463865 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": 1003345, "vin": [ { "gen": { "height": 1003335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "290f733a6b4d470f1d9d78a2394b4a2b1741bb70ddb98648d057ad503e94327b" } } ], "extra": [ 1, 122, 218, 15, 145, 155, 224, 175, 127, 226, 190, 212, 137, 62, 176, 202, 165, 91, 141, 249, 121, 99, 17, 76, 37, 134, 247, 44, 187, 107, 87, 85, 122, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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