Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8611a02a9993b417df6ea7ba298ae3c30478eb588ca22187c64417390c99104

Tx prefix hash: ebd63a19baac6df187b4366b7c4ffcfd83579c8c502f0043d5e5364148876f8c
Tx public key: 4ca46d5d422a434af0e6699484ba00ae4b839c3624a4042924c5b4be2c7274c2
Timestamp: 1712934441 Timestamp [UCT]: 2024-04-12 15:07:21 Age [y:d:h:m:s]: 01:219:04:54:02
Block: 998956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415363 RingCT/type: yes/0
Extra: 014ca46d5d422a434af0e6699484ba00ae4b839c3624a4042924c5b4be2c7274c20211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ae00bdd80162aac31f43f7fd30634a7da0909489a2c12199c5a96a131b49072 0.600000000000 1459432 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": 998966, "vin": [ { "gen": { "height": 998956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ae00bdd80162aac31f43f7fd30634a7da0909489a2c12199c5a96a131b49072" } } ], "extra": [ 1, 76, 164, 109, 93, 66, 42, 67, 74, 240, 230, 105, 148, 132, 186, 0, 174, 75, 131, 156, 54, 36, 164, 4, 41, 36, 197, 180, 190, 44, 114, 116, 194, 2, 17, 0, 0, 0, 4, 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