Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8fc0e82968ecbb32f83d7d5f30d354beaceb8d3beafeb8019eeb56555f59d9c

Tx prefix hash: 76839f6a7c51c02a7438b9accf8a526ae41616b79283fd422becfb2e212a766e
Tx public key: bc757914e1c97c2f8aeff247107fd2f6152b76b2af2d6a705b616b596404a697
Timestamp: 1581244031 Timestamp [UCT]: 2020-02-09 10:27:11 Age [y:d:h:m:s]: 04:323:09:02:10
Block: 61226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123272 RingCT/type: yes/0
Extra: 01bc757914e1c97c2f8aeff247107fd2f6152b76b2af2d6a705b616b596404a69702110000011412c4732d000000000000000000

1 output(s) for total of 384.710165721000 dcy

stealth address amount amount idx
00: 6fc17f3e934a03507d29452d742de34e99c18d0a2f575f3dba5118f9f2026bd3 384.710165721000 112822 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": 61236, "vin": [ { "gen": { "height": 61226 } } ], "vout": [ { "amount": 384710165721, "target": { "key": "6fc17f3e934a03507d29452d742de34e99c18d0a2f575f3dba5118f9f2026bd3" } } ], "extra": [ 1, 188, 117, 121, 20, 225, 201, 124, 47, 138, 239, 242, 71, 16, 127, 210, 246, 21, 43, 118, 178, 175, 45, 106, 112, 91, 97, 107, 89, 100, 4, 166, 151, 2, 17, 0, 0, 1, 20, 18, 196, 115, 45, 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