Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb0e79afa02ce284c4008b1eb41ed8a6a1d16b2253dca8f7d52cf7d75207bf5a

Tx prefix hash: f211081bbc939e4433fa28ce2efc21fa3d98dce5563828e68a6fa93dcb236548
Tx public key: 8361c08d62fd38fde9e2a08187c0d5d6b1a35af70151bc15316996102e266dfd
Timestamp: 1736484117 Timestamp [UCT]: 2025-01-10 04:41:57 Age [y:d:h:m:s]: 00:161:12:33:41
Block: 1194071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115122 RingCT/type: yes/0
Extra: 018361c08d62fd38fde9e2a08187c0d5d6b1a35af70151bc15316996102e266dfd0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9528e398438a5ef3e0d776b991c5f14589ef90ff402db284f1632f2a19547ae4 0.600000000000 1680638 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": 1194081, "vin": [ { "gen": { "height": 1194071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9528e398438a5ef3e0d776b991c5f14589ef90ff402db284f1632f2a19547ae4" } } ], "extra": [ 1, 131, 97, 192, 141, 98, 253, 56, 253, 233, 226, 160, 129, 135, 192, 213, 214, 177, 163, 90, 247, 1, 81, 188, 21, 49, 105, 150, 16, 46, 38, 109, 253, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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