Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4064529840a47a2b9f03718232a035e33a14c5e3362eff1a284b31e83eb2cd9f

Tx prefix hash: 92be48920b6b57f5cc42a8c9c02013a92165e7ecd79fb82c9da574381685f3e4
Tx public key: 3fc2e520436002d37767b163f0c7428e469e7ee5e45e1c47e3332d8472deec1a
Timestamp: 1715088202 Timestamp [UCT]: 2024-05-07 13:23:22 Age [y:d:h:m:s]: 00:136:23:22:06
Block: 1016841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98115 RingCT/type: yes/0
Extra: 013fc2e520436002d37767b163f0c7428e469e7ee5e45e1c47e3332d8472deec1a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b01c976f724e8beacd8a9b1da688b8602ce50e91fa5060df287ebaa83a4c4f3 0.600000000000 1480544 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": 1016851, "vin": [ { "gen": { "height": 1016841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b01c976f724e8beacd8a9b1da688b8602ce50e91fa5060df287ebaa83a4c4f3" } } ], "extra": [ 1, 63, 194, 229, 32, 67, 96, 2, 211, 119, 103, 177, 99, 240, 199, 66, 142, 70, 158, 126, 229, 228, 94, 28, 71, 227, 51, 45, 132, 114, 222, 236, 26, 2, 17, 0, 0, 0, 1, 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