Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bd523836a38fcdab4196a35b94506eb7f206107484f886f246957f77e7fa1e5

Tx prefix hash: 41e0347cd1be90074ab10e3f40e64418fd4751f7590e164ba19c10ea775d59d8
Tx public key: ac7d6c98db59dd14e558b1dcf8a22da4d8c13d17dcf3891578e29a2a33f24516
Timestamp: 1718097162 Timestamp [UCT]: 2024-06-11 09:12:42 Age [y:d:h:m:s]: 00:225:06:38:40
Block: 1041790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161158 RingCT/type: yes/0
Extra: 01ac7d6c98db59dd14e558b1dcf8a22da4d8c13d17dcf3891578e29a2a33f24516021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af09fdf4e6d06ff0396471627b5fb1d53c429a1f6e893db52b718a945c53c4c0 0.600000000000 1510551 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": 1041800, "vin": [ { "gen": { "height": 1041790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af09fdf4e6d06ff0396471627b5fb1d53c429a1f6e893db52b718a945c53c4c0" } } ], "extra": [ 1, 172, 125, 108, 152, 219, 89, 221, 20, 229, 88, 177, 220, 248, 162, 45, 164, 216, 193, 61, 23, 220, 243, 137, 21, 120, 226, 154, 42, 51, 242, 69, 22, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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