Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7be464b6e852e7389a5a2884da8827b645cdc1e9f5004dbe7ba8126dc82298

Tx prefix hash: 591fa079b38e729b28ecd48bc273c399073e2f50825e59613e3bd95c5ec57a8c
Tx public key: caba27043e6c18368d1cbefb8919e511e558ee245237547f47840e920e7dcfce
Timestamp: 1696394909 Timestamp [UCT]: 2023-10-04 04:48:29 Age [y:d:h:m:s]: 01:197:23:02:39
Block: 862056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402535 RingCT/type: yes/0
Extra: 01caba27043e6c18368d1cbefb8919e511e558ee245237547f47840e920e7dcfce02110000000ee6d27f9c000000000000000000

1 output(s) for total of 0.854379176000 dcy

stealth address amount amount idx
00: bcf7976b825e9f6d622659aa62f95a9bc84fddb6f6d34abca45e423a08118648 0.854379176000 1316436 of 0

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": 862066, "vin": [ { "gen": { "height": 862056 } } ], "vout": [ { "amount": 854379176, "target": { "key": "bcf7976b825e9f6d622659aa62f95a9bc84fddb6f6d34abca45e423a08118648" } } ], "extra": [ 1, 202, 186, 39, 4, 62, 108, 24, 54, 141, 28, 190, 251, 137, 25, 229, 17, 229, 88, 238, 36, 82, 55, 84, 127, 71, 132, 14, 146, 14, 125, 207, 206, 2, 17, 0, 0, 0, 14, 230, 210, 127, 156, 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