Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f887dd7f6fed0746ca7ef31eec0f8b033b66ebfdce98b7629c0529c17ebf3605

Tx prefix hash: a303af1d4730faa6367ed8af9801f5b54bc1ceec7765b3df8d0535c923fa4f5e
Tx public key: eba88d74e2720667292d89f28bc7f7e4372556f8afe4510580ab57963c712e80
Timestamp: 1581264680 Timestamp [UCT]: 2020-02-09 16:11:20 Age [y:d:h:m:s]: 04:320:08:51:55
Block: 61568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120966 RingCT/type: yes/0
Extra: 01eba88d74e2720667292d89f28bc7f7e4372556f8afe4510580ab57963c712e80021100000009c9f743ef000000000000000000

1 output(s) for total of 383.707664228000 dcy

stealth address amount amount idx
00: ee151c61a827a4dd924cd4af44169a1e1a9f8b5f6c2926f50345a40b9a349712 383.707664228000 113478 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": 61578, "vin": [ { "gen": { "height": 61568 } } ], "vout": [ { "amount": 383707664228, "target": { "key": "ee151c61a827a4dd924cd4af44169a1e1a9f8b5f6c2926f50345a40b9a349712" } } ], "extra": [ 1, 235, 168, 141, 116, 226, 114, 6, 103, 41, 45, 137, 242, 139, 199, 247, 228, 55, 37, 86, 248, 175, 228, 81, 5, 128, 171, 87, 150, 60, 113, 46, 128, 2, 17, 0, 0, 0, 9, 201, 247, 67, 239, 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