Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d37fa5b96656e76f3bcdb7f7cd1a171a2b49fa805cfc3a7181baa696b0a6b35

Tx prefix hash: e0b5cb92695d28e0a836fbf468db244709e2c056cbd332eb1ac0edc2d526057a
Tx public key: d69d7b182a4a5c04afa373603c93942994ba249e18baf30f8e812341af84b76a
Timestamp: 1705814113 Timestamp [UCT]: 2024-01-21 05:15:13 Age [y:d:h:m:s]: 01:093:19:15:40
Block: 939915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328145 RingCT/type: yes/0
Extra: 01d69d7b182a4a5c04afa373603c93942994ba249e18baf30f8e812341af84b76a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df33e1311b59ef4d6d603988f881ed80140c002321a71aa9502b2b0252ca466c 0.600000000000 1398049 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": 939925, "vin": [ { "gen": { "height": 939915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df33e1311b59ef4d6d603988f881ed80140c002321a71aa9502b2b0252ca466c" } } ], "extra": [ 1, 214, 157, 123, 24, 42, 74, 92, 4, 175, 163, 115, 96, 60, 147, 148, 41, 148, 186, 36, 158, 24, 186, 243, 15, 142, 129, 35, 65, 175, 132, 183, 106, 2, 17, 0, 0, 0, 1, 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