Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a342d24cfc296b61b9da1915aa3cf6bbfc417ca9077e1de0505d1c8fa946011

Tx prefix hash: ec44d067eec1c8d4b41c4e33acf85e17197e66552d1368679e0426555837c173
Tx public key: be64f1c33402fd93480b4e087f4db99eb4d1401dcf0c34aab5d1fc5e21877ac8
Timestamp: 1715042960 Timestamp [UCT]: 2024-05-07 00:49:20 Age [y:d:h:m:s]: 01:006:05:37:18
Block: 1016467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265368 RingCT/type: yes/0
Extra: 01be64f1c33402fd93480b4e087f4db99eb4d1401dcf0c34aab5d1fc5e21877ac80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b55e5a62af37bb47d541ec4c9e10c033dd7421c67ad4a95a904dbb7afe9662c 0.600000000000 1480060 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": 1016477, "vin": [ { "gen": { "height": 1016467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b55e5a62af37bb47d541ec4c9e10c033dd7421c67ad4a95a904dbb7afe9662c" } } ], "extra": [ 1, 190, 100, 241, 195, 52, 2, 253, 147, 72, 11, 78, 8, 127, 77, 185, 158, 180, 209, 64, 29, 207, 12, 52, 170, 181, 209, 252, 94, 33, 135, 122, 200, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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