Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e438e0ab9410697911676b8498ec1ffa9404ae20fa7f3ba6ae05db9b6a912489

Tx prefix hash: 170801e5a7e4d740619d4c4d2aba28147c00c5bdfd53be85268045c219bf8c5c
Tx public key: 12e903c037727c01280d7d248a4f7acaf9f7e1a3461d74953c1dc466281f4f04
Timestamp: 1581475831 Timestamp [UCT]: 2020-02-12 02:50:31 Age [y:d:h:m:s]: 04:356:15:57:53
Block: 63236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146727 RingCT/type: yes/0
Extra: 0112e903c037727c01280d7d248a4f7acaf9f7e1a3461d74953c1dc466281f4f040211000000120aca7173000000000000000000

1 output(s) for total of 378.855586027000 dcy

stealth address amount amount idx
00: 244da1e48b8d785bbf63b73aa76c49f46b672d4c82a0e91a522cee8c0c2f41d4 378.855586027000 116571 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": 63246, "vin": [ { "gen": { "height": 63236 } } ], "vout": [ { "amount": 378855586027, "target": { "key": "244da1e48b8d785bbf63b73aa76c49f46b672d4c82a0e91a522cee8c0c2f41d4" } } ], "extra": [ 1, 18, 233, 3, 192, 55, 114, 124, 1, 40, 13, 125, 36, 138, 79, 122, 202, 249, 247, 225, 163, 70, 29, 116, 149, 60, 29, 196, 102, 40, 31, 79, 4, 2, 17, 0, 0, 0, 18, 10, 202, 113, 115, 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