Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c79c1b11a20c20bcf01b354c6ba238f27e009c36d40d4b093ed24050c013dd74

Tx prefix hash: b1d23a3eeb13badae771817b6ce673f9b602ae8bea3c56d1938e047649d340a0
Tx public key: 0d4a7e0890484dbf95207f7f4fd3055e5bed050e97177069ed1cc60f7baa5cd4
Timestamp: 1713996388 Timestamp [UCT]: 2024-04-24 22:06:28 Age [y:d:h:m:s]: 01:000:02:56:11
Block: 1007786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261023 RingCT/type: yes/0
Extra: 010d4a7e0890484dbf95207f7f4fd3055e5bed050e97177069ed1cc60f7baa5cd40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4934c51018a14ee69757a49b754efad42b094c651c9d393d4ad9183d1120925 0.600000000000 1469234 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": 1007796, "vin": [ { "gen": { "height": 1007786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4934c51018a14ee69757a49b754efad42b094c651c9d393d4ad9183d1120925" } } ], "extra": [ 1, 13, 74, 126, 8, 144, 72, 77, 191, 149, 32, 127, 127, 79, 211, 5, 94, 91, 237, 5, 14, 151, 23, 112, 105, 237, 28, 198, 15, 123, 170, 92, 212, 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