Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b62f982f6b0bd9309086ab6b61e8ce116de582be605c830b8d8831b7b43ad073

Tx prefix hash: 189b652b5e14410bf35cdbc07c711e75d537036984a44b8f4ebc720dc2093b00
Tx public key: e8a9da7e77b84e572ce5a159b15411dc13deae1917ad0bb4466a24efb311e3ab
Timestamp: 1649543889 Timestamp [UCT]: 2022-04-09 22:38:09 Age [y:d:h:m:s]: 02:310:04:42:59
Block: 476854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 741245 RingCT/type: yes/0
Extra: 01e8a9da7e77b84e572ce5a159b15411dc13deae1917ad0bb4466a24efb311e3ab021100000008c9067537000000000000000000

1 output(s) for total of 16.143027475000 dcy

stealth address amount amount idx
00: 09b8a591a2e74ff1f3c3cdc5633d5f30247bf1b8eb1433ede56a042bdf7f601c 16.143027475000 897427 of 0

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": 476864, "vin": [ { "gen": { "height": 476854 } } ], "vout": [ { "amount": 16143027475, "target": { "key": "09b8a591a2e74ff1f3c3cdc5633d5f30247bf1b8eb1433ede56a042bdf7f601c" } } ], "extra": [ 1, 232, 169, 218, 126, 119, 184, 78, 87, 44, 229, 161, 89, 177, 84, 17, 220, 19, 222, 174, 25, 23, 173, 11, 180, 70, 106, 36, 239, 179, 17, 227, 171, 2, 17, 0, 0, 0, 8, 201, 6, 117, 55, 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