Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d878ddaf4559c33433323ad3b7e567e4578b7feefb4afd760f31dd3cea12a3c2

Tx prefix hash: 29e08e818d4f6c120f996e93955db246e3b02a09c1d715243cc5792c033c8109
Tx public key: bfccf6f61390e6aafa12bf7dea11f3b3ad6be28294d123141f447ad9a15d5624
Timestamp: 1580567616 Timestamp [UCT]: 2020-02-01 14:33:36 Age [y:d:h:m:s]: 04:326:04:14:08
Block: 56518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124422 RingCT/type: yes/0
Extra: 01bfccf6f61390e6aafa12bf7dea11f3b3ad6be28294d123141f447ad9a15d56240211000000034ac5aa02000000000000000000

1 output(s) for total of 398.779870223000 dcy

stealth address amount amount idx
00: fac0562f13a5f81caaceab60fb945fe4dcd7f396505ae7ee6143dc5623b92293 398.779870223000 104251 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": 56528, "vin": [ { "gen": { "height": 56518 } } ], "vout": [ { "amount": 398779870223, "target": { "key": "fac0562f13a5f81caaceab60fb945fe4dcd7f396505ae7ee6143dc5623b92293" } } ], "extra": [ 1, 191, 204, 246, 246, 19, 144, 230, 170, 250, 18, 191, 125, 234, 17, 243, 179, 173, 107, 226, 130, 148, 209, 35, 20, 31, 68, 122, 217, 161, 93, 86, 36, 2, 17, 0, 0, 0, 3, 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