Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c6285c9bdc6409afec7f55dc40cf13a33a5972380008e17001def893b8079a

Tx prefix hash: 232a7f6c6513a615840a1f169a32196dd23fe65bdab5bed45224dfc8e19d9ae1
Tx public key: a87632045064daa405f6279c7a3e3c52add723c3ed2de45688ed5d5266ab6778
Timestamp: 1710310945 Timestamp [UCT]: 2024-03-13 06:22:25 Age [y:d:h:m:s]: 01:020:04:27:14
Block: 977240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275407 RingCT/type: yes/0
Extra: 01a87632045064daa405f6279c7a3e3c52add723c3ed2de45688ed5d5266ab677802110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bc04a7a4871ca7fcf2cf98ae53d1bccff53ff10179a398c810c80cb87e5b352 0.600000000000 1437241 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": 977250, "vin": [ { "gen": { "height": 977240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bc04a7a4871ca7fcf2cf98ae53d1bccff53ff10179a398c810c80cb87e5b352" } } ], "extra": [ 1, 168, 118, 50, 4, 80, 100, 218, 164, 5, 246, 39, 156, 122, 62, 60, 82, 173, 215, 35, 195, 237, 45, 228, 86, 136, 237, 93, 82, 102, 171, 103, 120, 2, 17, 0, 0, 0, 12, 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