Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2ea7736b58a1ad99d60d056b5c26b4aba4a0c4cbe379338131074f9e819ab4

Tx prefix hash: 97f478e598a85f20e51a7e85bf721cec498bc6e1d8f9db835eb9667687249f87
Tx public key: 322d1e13e0e7b7656acc0587c604af5316f857d689bf0e86dab5be531a920e0a
Timestamp: 1721913366 Timestamp [UCT]: 2024-07-25 13:16:06 Age [y:d:h:m:s]: 00:258:23:00:08
Block: 1073418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184995 RingCT/type: yes/0
Extra: 01322d1e13e0e7b7656acc0587c604af5316f857d689bf0e86dab5be531a920e0a02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85f1014c785e6d60ad2059e85801aa4bd615c6bb79d7ee22d93174b3469b25d7 0.600000000000 1545919 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": 1073428, "vin": [ { "gen": { "height": 1073418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85f1014c785e6d60ad2059e85801aa4bd615c6bb79d7ee22d93174b3469b25d7" } } ], "extra": [ 1, 50, 45, 30, 19, 224, 231, 183, 101, 106, 204, 5, 135, 198, 4, 175, 83, 22, 248, 87, 214, 137, 191, 14, 134, 218, 181, 190, 83, 26, 146, 14, 10, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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