Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b0d3b4d07db40222bd9281082cea9aa29a055abe6c5c7e21d74cbdf3ff3c9f8

Tx prefix hash: 8e5aff8ba88a20a02e0860ac822a5acfb35220715af98a2d63c05309ca99b28b
Tx public key: 1137cc47cdee9ae6596c62574e19dd4537b9ca3d0644ba41d01480088d6961da
Timestamp: 1713536597 Timestamp [UCT]: 2024-04-19 14:23:17 Age [y:d:h:m:s]: 01:172:09:14:05
Block: 1003969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381808 RingCT/type: yes/0
Extra: 011137cc47cdee9ae6596c62574e19dd4537b9ca3d0644ba41d01480088d6961da02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 356b7ccb76ddcbe37ffbd6ea45662bbc3aae3b5dca3c309e3d4de2db551497b5 0.600000000000 1464525 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": 1003979, "vin": [ { "gen": { "height": 1003969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "356b7ccb76ddcbe37ffbd6ea45662bbc3aae3b5dca3c309e3d4de2db551497b5" } } ], "extra": [ 1, 17, 55, 204, 71, 205, 238, 154, 230, 89, 108, 98, 87, 78, 25, 221, 69, 55, 185, 202, 61, 6, 68, 186, 65, 208, 20, 128, 8, 141, 105, 97, 218, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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