Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf4bbd9b74cc3dfae45d359784120f70de8b83939b8afc6b8868898c646cb128

Tx prefix hash: 2661bdc0dad8e8714415d4c3e0e86019e8429ec4f60a76832e8dcbafd736b7f9
Tx public key: 63fb03c3d217c0110a4624cc7cbf1a4f4f5d00ae3a757ad4b31a72da4beabe6a
Timestamp: 1706751024 Timestamp [UCT]: 2024-02-01 01:30:24 Age [y:d:h:m:s]: 01:069:07:07:14
Block: 947696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310604 RingCT/type: yes/0
Extra: 0163fb03c3d217c0110a4624cc7cbf1a4f4f5d00ae3a757ad4b31a72da4beabe6a02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7f99ce544140a39df8eee8b1e044c21b94489f2b9b3af6b7ef97def8b0d7399 0.600000000000 1406054 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": 947706, "vin": [ { "gen": { "height": 947696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7f99ce544140a39df8eee8b1e044c21b94489f2b9b3af6b7ef97def8b0d7399" } } ], "extra": [ 1, 99, 251, 3, 195, 210, 23, 192, 17, 10, 70, 36, 204, 124, 191, 26, 79, 79, 93, 0, 174, 58, 117, 122, 212, 179, 26, 114, 218, 75, 234, 190, 106, 2, 17, 0, 0, 0, 5, 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