Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 092e0ebf9a6c7ae6ec905a039df83e7bd1b82f02012a5ac6059f49c6851f4ea0

Tx prefix hash: a337c26f2db62b5d2bcfc954d4629536898607b1fb30d30bb3c4840fb020d258
Tx public key: 9ccc5997964519ce950988e2ebe236206d706eeb707c0ebf35d712a8cca9a978
Timestamp: 1700839151 Timestamp [UCT]: 2023-11-24 15:19:11 Age [y:d:h:m:s]: 01:152:15:51:41
Block: 898702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370293 RingCT/type: yes/0
Extra: 019ccc5997964519ce950988e2ebe236206d706eeb707c0ebf35d712a8cca9a978021100000005faf35c9c000000000000000000

1 output(s) for total of 0.645992075000 dcy

stealth address amount amount idx
00: f154848645e5c97c4533f51907ddaf7fca88ffcdb3b240f04eef1214ea8435d9 0.645992075000 1355135 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": 898712, "vin": [ { "gen": { "height": 898702 } } ], "vout": [ { "amount": 645992075, "target": { "key": "f154848645e5c97c4533f51907ddaf7fca88ffcdb3b240f04eef1214ea8435d9" } } ], "extra": [ 1, 156, 204, 89, 151, 150, 69, 25, 206, 149, 9, 136, 226, 235, 226, 54, 32, 109, 112, 110, 235, 112, 124, 14, 191, 53, 215, 18, 168, 204, 169, 169, 120, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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