Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28d241419d2c23737b7a1dab838dc766d7065e13bf9e18feabd5d4fd92372a80

Tx prefix hash: b242b229545f314bfbda709410383dd400b74bc136c7a5d77051b9b8b74e27db
Tx public key: 141ff0da9fc86b1601b3b7caab9528e8411d4ebe96d572ca417ab5d2cb21c19c
Timestamp: 1579270680 Timestamp [UCT]: 2020-01-17 14:18:00 Age [y:d:h:m:s]: 05:120:01:10:41
Block: 47585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1235961 RingCT/type: yes/0
Extra: 01141ff0da9fc86b1601b3b7caab9528e8411d4ebe96d572ca417ab5d2cb21c19c0211000000284ac5aa02000000000000000000

1 output(s) for total of 426.905724133000 dcy

stealth address amount amount idx
00: 20578fc5c627948106af2e3523139f91520cd9765dc3fb91d953ff8e467f7356 426.905724133000 87952 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": 47595, "vin": [ { "gen": { "height": 47585 } } ], "vout": [ { "amount": 426905724133, "target": { "key": "20578fc5c627948106af2e3523139f91520cd9765dc3fb91d953ff8e467f7356" } } ], "extra": [ 1, 20, 31, 240, 218, 159, 200, 107, 22, 1, 179, 183, 202, 171, 149, 40, 232, 65, 29, 78, 190, 150, 213, 114, 202, 65, 122, 181, 210, 203, 33, 193, 156, 2, 17, 0, 0, 0, 40, 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