Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4929787dfe5398616be03d615f97b916fb911721144804179d9dcc7a98eb3901

Tx prefix hash: 9e467faf68cd83dbf7afb68d7d731dc22d4b131e68e8fef8c6ae0ef9e0ab9866
Tx public key: d271e16e98c668e8ba6f0c24c2f36780ace17d820b6bb2d6970ad7b2f43cd4f4
Timestamp: 1643297824 Timestamp [UCT]: 2022-01-27 15:37:04 Age [y:d:h:m:s]: 02:363:02:09:59
Block: 426436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 777999 RingCT/type: yes/0
Extra: 01d271e16e98c668e8ba6f0c24c2f36780ace17d820b6bb2d6970ad7b2f43cd4f402110000002ea9aaab5d000000000000000000

1 output(s) for total of 23.715966231000 dcy

stealth address amount amount idx
00: 7753f4e39943b0309055d0fb898a6ee92dfb2779c0eadf7d8f4acf75b4221973 23.715966231000 835263 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": 426446, "vin": [ { "gen": { "height": 426436 } } ], "vout": [ { "amount": 23715966231, "target": { "key": "7753f4e39943b0309055d0fb898a6ee92dfb2779c0eadf7d8f4acf75b4221973" } } ], "extra": [ 1, 210, 113, 225, 110, 152, 198, 104, 232, 186, 111, 12, 36, 194, 243, 103, 128, 172, 225, 125, 130, 11, 107, 178, 214, 151, 10, 215, 178, 244, 60, 212, 244, 2, 17, 0, 0, 0, 46, 169, 170, 171, 93, 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