Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd004ab4f3827618c3db5a2cb2db7c2cd5e68f58a58b61d291cae06969bb4512

Tx prefix hash: ea712d2ab954894aaee73876f7c2c44eaf78e2803315dd205ad0382eb1193454
Tx public key: 721db06e507daff4cd3bc7b1eee5cc53cce8e5e7855b78d2398f841e346e5eb6
Timestamp: 1731489567 Timestamp [UCT]: 2024-11-13 09:19:27 Age [y:d:h:m:s]: 00:123:19:43:28
Block: 1152717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88327 RingCT/type: yes/0
Extra: 01721db06e507daff4cd3bc7b1eee5cc53cce8e5e7855b78d2398f841e346e5eb6021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 197135a4cc9c2350d882990f167111318d302d420cc218f0cb55fe1d27458549 0.600000000000 1638320 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": 1152727, "vin": [ { "gen": { "height": 1152717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "197135a4cc9c2350d882990f167111318d302d420cc218f0cb55fe1d27458549" } } ], "extra": [ 1, 114, 29, 176, 110, 80, 125, 175, 244, 205, 59, 199, 177, 238, 229, 204, 83, 204, 232, 229, 231, 133, 91, 120, 210, 57, 143, 132, 30, 52, 110, 94, 182, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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