Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c87a79ec2b584671ab7b07703a54c18589e07b94dfb6a711e921f1a3aa11d75

Tx prefix hash: 53d7b6fed952cddd574fd806075c4d7f3521247a52167c7b3129f8a7f12dbcd1
Tx public key: 27056510e87a74e4ac3b0367ceb76bea24736b79c3457fd2ee3487706c912917
Timestamp: 1574550072 Timestamp [UCT]: 2019-11-23 23:01:12 Age [y:d:h:m:s]: 05:076:03:50:00
Block: 15983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1197087 RingCT/type: yes/0
Extra: 0127056510e87a74e4ac3b0367ceb76bea24736b79c3457fd2ee3487706c912917021100000009f95225a5000000000000000000

1 output(s) for total of 543.303582638000 dcy

stealth address amount amount idx
00: 39c07059a9dac05357e690ef6d6d863edbdf11e73efb1195f1cb5971bad288a0 543.303582638000 21940 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": 15993, "vin": [ { "gen": { "height": 15983 } } ], "vout": [ { "amount": 543303582638, "target": { "key": "39c07059a9dac05357e690ef6d6d863edbdf11e73efb1195f1cb5971bad288a0" } } ], "extra": [ 1, 39, 5, 101, 16, 232, 122, 116, 228, 172, 59, 3, 103, 206, 183, 107, 234, 36, 115, 107, 121, 195, 69, 127, 210, 238, 52, 135, 112, 108, 145, 41, 23, 2, 17, 0, 0, 0, 9, 249, 82, 37, 165, 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