Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a648ddb253354d1bf183a6506b64c233f93dc163fefa8fa8b87266bb680497f

Tx prefix hash: a6d6db19c9fd7da2e38f05fa652bd5a3abb41f81e819294dde0f64ff521e3349
Tx public key: e83f1061829604d62c91d5969df1de441fd3a6f057aa58d7b2fc6eac3586abb9
Timestamp: 1733604510 Timestamp [UCT]: 2024-12-07 20:48:30 Age [y:d:h:m:s]: 00:144:06:23:58
Block: 1170240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102905 RingCT/type: yes/0
Extra: 01e83f1061829604d62c91d5969df1de441fd3a6f057aa58d7b2fc6eac3586abb9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4623e6d09107c69286fe9246c1e1cf8bc83acb265c6c0ae18359d01966c3869 0.600000000000 1655969 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": 1170250, "vin": [ { "gen": { "height": 1170240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4623e6d09107c69286fe9246c1e1cf8bc83acb265c6c0ae18359d01966c3869" } } ], "extra": [ 1, 232, 63, 16, 97, 130, 150, 4, 214, 44, 145, 213, 150, 157, 241, 222, 68, 31, 211, 166, 240, 87, 170, 88, 215, 178, 252, 110, 172, 53, 134, 171, 185, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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