Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d75fe658322661b9a67466d91f6ad09d720601fb1d319bb88388e2649a33440

Tx prefix hash: 235ec694755d8e8f795b5f9c4f8d909e0b627c7c9a7c370f7b3bdd132696b9aa
Tx public key: a15206834486c0f61217109ffa4f1e1df82d4283837e46cb431e0ddd01f96bb1
Timestamp: 1749141609 Timestamp [UCT]: 2025-06-05 16:40:09 Age [y:d:h:m:s]: 00:158:08:34:44
Block: 1298627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110828 RingCT/type: yes/0
Extra: 01a15206834486c0f61217109ffa4f1e1df82d4283837e46cb431e0ddd01f96bb1021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 840fd6c014bea20663e0d20b2e8f0705c8a19ff099be0804e3247e912c433a2f 0.600000000000 1786156 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": 1298637, "vin": [ { "gen": { "height": 1298627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "840fd6c014bea20663e0d20b2e8f0705c8a19ff099be0804e3247e912c433a2f" } } ], "extra": [ 1, 161, 82, 6, 131, 68, 134, 192, 246, 18, 23, 16, 159, 250, 79, 30, 29, 248, 45, 66, 131, 131, 126, 70, 203, 67, 30, 13, 221, 1, 249, 107, 177, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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