Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ded1309d52c535f3e54c2a5cba2b58b6bd096646e2b357f691d56e2e467f8f0b

Tx prefix hash: 6392629086be6d0c1518af4f1c5090d4e7a0277b22c572c345d0c9b8d49fa833
Tx public key: 97ad087612388bc96c20b69ca5f4d61b04a1abe85d0d5fed40987c2d5f63f507
Timestamp: 1649656384 Timestamp [UCT]: 2022-04-11 05:53:04 Age [y:d:h:m:s]: 02:234:04:41:28
Block: 477776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687147 RingCT/type: yes/0
Extra: 0197ad087612388bc96c20b69ca5f4d61b04a1abe85d0d5fed40987c2d5f63f5070211000000024da16a3a000000000000000000

1 output(s) for total of 16.029870573000 dcy

stealth address amount amount idx
00: 9a64390e34d1e86646d2b2bff22e55f3b241ea1f5db8bfb283a26dcc315226c3 16.029870573000 898467 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": 477786, "vin": [ { "gen": { "height": 477776 } } ], "vout": [ { "amount": 16029870573, "target": { "key": "9a64390e34d1e86646d2b2bff22e55f3b241ea1f5db8bfb283a26dcc315226c3" } } ], "extra": [ 1, 151, 173, 8, 118, 18, 56, 139, 201, 108, 32, 182, 156, 165, 244, 214, 27, 4, 161, 171, 232, 93, 13, 95, 237, 64, 152, 124, 45, 95, 99, 245, 7, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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