Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d406291e0bce4a7a199445f81e749c73c5798e8d9a3ad1e7d0390a48b524f76

Tx prefix hash: fccfa470c5e3f36d8737a45f2eacd9be73abfd8a7c5011cb4014e253c4b743e0
Tx public key: 66df44b33d3dc4d8fbc6c75f0a143490fff757a2b46fb0e491834f4999860c4b
Timestamp: 1682845350 Timestamp [UCT]: 2023-04-30 09:02:30 Age [y:d:h:m:s]: 01:182:01:27:01
Block: 749774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391538 RingCT/type: yes/0
Extra: 0166df44b33d3dc4d8fbc6c75f0a143490fff757a2b46fb0e491834f4999860c4b02110000000433af99f4000000000000000000

1 output(s) for total of 2.012276686000 dcy

stealth address amount amount idx
00: 1449f98cb3a18355ce5788c7fbca227103721c408340126add19557adbb9a916 2.012276686000 1197779 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": 749784, "vin": [ { "gen": { "height": 749774 } } ], "vout": [ { "amount": 2012276686, "target": { "key": "1449f98cb3a18355ce5788c7fbca227103721c408340126add19557adbb9a916" } } ], "extra": [ 1, 102, 223, 68, 179, 61, 61, 196, 216, 251, 198, 199, 95, 10, 20, 52, 144, 255, 247, 87, 162, 180, 111, 176, 228, 145, 131, 79, 73, 153, 134, 12, 75, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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