Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffdc16c63af2e5b4dc2331a3cbc85b56063ea4e43e3c1971435cd24fa1bb44d2

Tx prefix hash: fa0ca993dfa8f5ee537a4e5d3cd09f3d1d3d0a7cd78fb92960e13d984bbeb598
Tx public key: ab5502f617311b75174d6ed76ac817807f9660baeeb5a5f4c97a289738d40c89
Timestamp: 1576192584 Timestamp [UCT]: 2019-12-12 23:16:24 Age [y:d:h:m:s]: 06:006:19:35:38
Block: 26301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1409453 RingCT/type: yes/0
Extra: 01ab5502f617311b75174d6ed76ac817807f9660baeeb5a5f4c97a289738d40c8902110000001a4ac5aa02000000000000000000

1 output(s) for total of 502.180493444000 dcy

stealth address amount amount idx
00: deacbf296f276e78f6254f2d70c6d21506501afde56974ad895d8c44fa5c640e 502.180493444000 43424 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": 26311, "vin": [ { "gen": { "height": 26301 } } ], "vout": [ { "amount": 502180493444, "target": { "key": "deacbf296f276e78f6254f2d70c6d21506501afde56974ad895d8c44fa5c640e" } } ], "extra": [ 1, 171, 85, 2, 246, 23, 49, 27, 117, 23, 77, 110, 215, 106, 200, 23, 128, 127, 150, 96, 186, 238, 181, 165, 244, 201, 122, 40, 151, 56, 212, 12, 137, 2, 17, 0, 0, 0, 26, 74, 197, 170, 2, 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