Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad2892fe5f439da87fa1634a23df81a27e406f6559c238a54b921832e71de5dd

Tx prefix hash: ee4c1fac1902662c7d11160a96d624cb27d36a6de232a6254a4ca4200de4fc7d
Tx public key: bd6f670c47e92ad76f00dfd18a9e9e9b12abe5e5588322e0cc3a6f84733f4013
Timestamp: 1588265177 Timestamp [UCT]: 2020-04-30 16:46:17 Age [y:d:h:m:s]: 04:305:14:22:49
Block: 97071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132569 RingCT/type: yes/0
Extra: 01bd6f670c47e92ad76f00dfd18a9e9e9b12abe5e5588322e0cc3a6f84733f401302110000074a86362411000000000000000000

1 output(s) for total of 292.660592234000 dcy

stealth address amount amount idx
00: f1095469006a434a80c68447017e9a8150361a16142a5ba988404d0c96099cf8 292.660592234000 172078 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": 97081, "vin": [ { "gen": { "height": 97071 } } ], "vout": [ { "amount": 292660592234, "target": { "key": "f1095469006a434a80c68447017e9a8150361a16142a5ba988404d0c96099cf8" } } ], "extra": [ 1, 189, 111, 103, 12, 71, 233, 42, 215, 111, 0, 223, 209, 138, 158, 158, 155, 18, 171, 229, 229, 88, 131, 34, 224, 204, 58, 111, 132, 115, 63, 64, 19, 2, 17, 0, 0, 7, 74, 134, 54, 36, 17, 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