Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cddf028376f942d7c0b7437a97f10711c3c77d96622d519d7ad8755b31e4a8ab

Tx prefix hash: a8deac445097f6b8183a2c6920168b7106d01fb5becccd428687c3879009eafd
Tx public key: 447289576d00ba8b9b4b8f5633550d82939b9cf1a401f844332c07bb86c0fd5a
Timestamp: 1725054665 Timestamp [UCT]: 2024-08-30 21:51:05 Age [y:d:h:m:s]: 01:061:03:38:03
Block: 1099452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302156 RingCT/type: yes/0
Extra: 01447289576d00ba8b9b4b8f5633550d82939b9cf1a401f844332c07bb86c0fd5a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bd7b446289ba73a1d1ef94731503e2d543d3ed7405f76e3601ab2cc7ad06e6b 0.600000000000 1575413 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": 1099462, "vin": [ { "gen": { "height": 1099452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bd7b446289ba73a1d1ef94731503e2d543d3ed7405f76e3601ab2cc7ad06e6b" } } ], "extra": [ 1, 68, 114, 137, 87, 109, 0, 186, 139, 155, 75, 143, 86, 51, 85, 13, 130, 147, 155, 156, 241, 164, 1, 248, 68, 51, 44, 7, 187, 134, 192, 253, 90, 2, 17, 0, 0, 0, 3, 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