Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3743a33296c7ca1f471d4fda1a9ffeaafc3c2ab87d835d5b1df3456446195e8

Tx prefix hash: f2f3dcae3e9293d6b369ca2f501375bf2c00e317574b36142972d323e9531138
Tx public key: c74c5020bcd026cffe89d3fb4a1470d2d1cd8aa7040113b7b5984bdae8d6f1a3
Timestamp: 1717736614 Timestamp [UCT]: 2024-06-07 05:03:34 Age [y:d:h:m:s]: 00:283:01:00:30
Block: 1038791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202285 RingCT/type: yes/0
Extra: 01c74c5020bcd026cffe89d3fb4a1470d2d1cd8aa7040113b7b5984bdae8d6f1a302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 900c86d861e1d5328e3db55032e21f15af25ef7810caa539de17ae06e032c7a2 0.600000000000 1507352 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": 1038801, "vin": [ { "gen": { "height": 1038791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "900c86d861e1d5328e3db55032e21f15af25ef7810caa539de17ae06e032c7a2" } } ], "extra": [ 1, 199, 76, 80, 32, 188, 208, 38, 207, 254, 137, 211, 251, 74, 20, 112, 210, 209, 205, 138, 167, 4, 1, 19, 183, 181, 152, 75, 218, 232, 214, 241, 163, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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