Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e997d229a1bff2baea8c0539c15e999587183d5749e5c4ae295a2ac76e21cae4

Tx prefix hash: ab75e8bd114b152fde584b743f4dcc99a690e5ceaaf3ad5df03ace5a7e455fe7
Tx public key: 88e51a0fe2029e1ace68f685b4b54700eedfec6a1824a12c2a2fab3505186727
Timestamp: 1576643807 Timestamp [UCT]: 2019-12-18 04:36:47 Age [y:d:h:m:s]: 05:082:15:24:53
Block: 28406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1206642 RingCT/type: yes/0
Extra: 0188e51a0fe2029e1ace68f685b4b54700eedfec6a1824a12c2a2fab35051867270211000000369159db1e000000000000000000

1 output(s) for total of 494.174116766000 dcy

stealth address amount amount idx
00: 003882c66153072e6cfe91d5bc7b19b29a9c8d7c362911e3b4e363209377c8e5 494.174116766000 46950 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": 28416, "vin": [ { "gen": { "height": 28406 } } ], "vout": [ { "amount": 494174116766, "target": { "key": "003882c66153072e6cfe91d5bc7b19b29a9c8d7c362911e3b4e363209377c8e5" } } ], "extra": [ 1, 136, 229, 26, 15, 226, 2, 158, 26, 206, 104, 246, 133, 180, 181, 71, 0, 238, 223, 236, 106, 24, 36, 161, 44, 42, 47, 171, 53, 5, 24, 103, 39, 2, 17, 0, 0, 0, 54, 145, 89, 219, 30, 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