Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c820cda43f6c5b27e17dcd9d97c6a7b71b565941a5b7c892dcda35be47d4d2bf

Tx prefix hash: 7e46d24def79f24e2b285fb2c991ba4ff3edda04f378a9bc3b24c3b6c3f616e5
Tx public key: cc6934ebb0584e8208a42bcba52b02b563df3ea18b21577e845370dd40f4ee85
Timestamp: 1745813863 Timestamp [UCT]: 2025-04-28 04:17:43 Age [y:d:h:m:s]: 00:010:10:49:36
Block: 1271053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7462 RingCT/type: yes/0
Extra: 01cc6934ebb0584e8208a42bcba52b02b563df3ea18b21577e845370dd40f4ee850211000000099f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da1431f70fd75d310b3eca4c1493b0e3886020fed32e394ad06dd483bdbf4207 0.600000000000 1758300 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": 1271063, "vin": [ { "gen": { "height": 1271053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da1431f70fd75d310b3eca4c1493b0e3886020fed32e394ad06dd483bdbf4207" } } ], "extra": [ 1, 204, 105, 52, 235, 176, 88, 78, 130, 8, 164, 43, 203, 165, 43, 2, 181, 99, 223, 62, 161, 139, 33, 87, 126, 132, 83, 112, 221, 64, 244, 238, 133, 2, 17, 0, 0, 0, 9, 159, 159, 230, 140, 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