Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b4ea3d8d17f28b28e866d36fb7632ff4c2db5cf00b83265c1934b16f9eefd32

Tx prefix hash: b492003ffa87cf1b0165da9cb572190181a98ff8c2318da4ee68b3c7328ec7e5
Tx public key: b7af662fae70e10d5380f39541602b1d0ad6a1ba6f0223abdec0c08298a364f8
Timestamp: 1726133015 Timestamp [UCT]: 2024-09-12 09:23:35 Age [y:d:h:m:s]: 00:207:11:45:54
Block: 1108391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148117 RingCT/type: yes/0
Extra: 01b7af662fae70e10d5380f39541602b1d0ad6a1ba6f0223abdec0c08298a364f802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a800680d746db934358b4a6cdf45ff8a121521be1614fff2e33b787a1ecb4361 0.600000000000 1586270 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": 1108401, "vin": [ { "gen": { "height": 1108391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a800680d746db934358b4a6cdf45ff8a121521be1614fff2e33b787a1ecb4361" } } ], "extra": [ 1, 183, 175, 102, 47, 174, 112, 225, 13, 83, 128, 243, 149, 65, 96, 43, 29, 10, 214, 161, 186, 111, 2, 35, 171, 222, 192, 192, 130, 152, 163, 100, 248, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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