Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c21cf1951384f9c0cc0fd6aa1041ac79d446a463a32966706928a11bea9b836

Tx prefix hash: 70a0984d08b1ec4f17d6e00ce4e8373670819c1bc6745cea312eeb325d21cc40
Tx public key: 8927136f48a9ea6339f331b1e8e17a00920c768ea4eaade7ca6f71f09aa0224f
Timestamp: 1712572470 Timestamp [UCT]: 2024-04-08 10:34:30 Age [y:d:h:m:s]: 01:038:16:22:25
Block: 995945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288658 RingCT/type: yes/0
Extra: 018927136f48a9ea6339f331b1e8e17a00920c768ea4eaade7ca6f71f09aa0224f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 221c7b41a430b728946c2044fcf1b64d51752141fedb820c1259b3a5ddc3aca6 0.600000000000 1456361 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": 995955, "vin": [ { "gen": { "height": 995945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "221c7b41a430b728946c2044fcf1b64d51752141fedb820c1259b3a5ddc3aca6" } } ], "extra": [ 1, 137, 39, 19, 111, 72, 169, 234, 99, 57, 243, 49, 177, 232, 225, 122, 0, 146, 12, 118, 142, 164, 234, 173, 231, 202, 111, 113, 240, 154, 160, 34, 79, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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