Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18b15fbade90b5b5305966d192aa6f223cb91eb04ddba1c361ede5b65534b2be

Tx prefix hash: 2ae7138f195643523574cac73da6203a435d7d346587c1cd9e22af775e9074de
Tx public key: 19a94f0cf7c36252a93a6c5b2b6feb990fc694316f90402c9eaec9d3175223b0
Timestamp: 1727384512 Timestamp [UCT]: 2024-09-26 21:01:52 Age [y:d:h:m:s]: 00:186:04:33:04
Block: 1118774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132873 RingCT/type: yes/0
Extra: 0119a94f0cf7c36252a93a6c5b2b6feb990fc694316f90402c9eaec9d3175223b0021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e692508b5e185c26e10d632d9c058727234d309bd91a87af40445373a4238ff4 0.600000000000 1600085 of 15

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": 1118784, "vin": [ { "gen": { "height": 1118774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e692508b5e185c26e10d632d9c058727234d309bd91a87af40445373a4238ff4" } } ], "extra": [ 1, 25, 169, 79, 12, 247, 195, 98, 82, 169, 58, 108, 91, 43, 111, 235, 153, 15, 198, 148, 49, 111, 144, 64, 44, 158, 174, 201, 211, 23, 82, 35, 176, 2, 17, 0, 0, 0, 20, 233, 20, 221, 21, 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