Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2264da1bc4c01d6d3495a31aa4ebec6c747b6137a3921aa334c205085ed2b8dd

Tx prefix hash: a0333e74a7a513a9a61985b088c2be312318442d580d008d6f2130df742b27f2
Tx public key: dd37ff29778f49bc7a3186c5ee87717365c60f0859028c0bb763c936b751272a
Timestamp: 1709940570 Timestamp [UCT]: 2024-03-08 23:29:30 Age [y:d:h:m:s]: 01:272:00:07:05
Block: 974167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453139 RingCT/type: yes/0
Extra: 01dd37ff29778f49bc7a3186c5ee87717365c60f0859028c0bb763c936b751272a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cee7a6ec9b28073c6b587e4abd6239182fb6b92c925005afc98e7c5bdaa7625 0.600000000000 1434118 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": 974177, "vin": [ { "gen": { "height": 974167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cee7a6ec9b28073c6b587e4abd6239182fb6b92c925005afc98e7c5bdaa7625" } } ], "extra": [ 1, 221, 55, 255, 41, 119, 143, 73, 188, 122, 49, 134, 197, 238, 135, 113, 115, 101, 198, 15, 8, 89, 2, 140, 11, 183, 99, 201, 54, 183, 81, 39, 42, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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