Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8fd486ac4e11814e044554b85cb02441f6959a7b32f34b047641aa9cf592111

Tx prefix hash: 08a81ef7d879786c581cc289b3bbdc5d6954ff663b5d16cb1ae8562b15b13d8c
Tx public key: 33efe25095d7b39369184c4f1eb4f5e26fb8eca030dc13b39007211f38ca27c0
Timestamp: 1751309689 Timestamp [UCT]: 2025-06-30 18:54:49 Age [y:d:h:m:s]: 00:138:07:33:21
Block: 1316030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97049 RingCT/type: yes/0
Extra: 0133efe25095d7b39369184c4f1eb4f5e26fb8eca030dc13b39007211f38ca27c0021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c47767d77ac01b3cf95dcb0ebbb345befb1efcfbbcc2edc091e14ff205cf4e6 0.600000000000 1803687 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": 1316040, "vin": [ { "gen": { "height": 1316030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c47767d77ac01b3cf95dcb0ebbb345befb1efcfbbcc2edc091e14ff205cf4e6" } } ], "extra": [ 1, 51, 239, 226, 80, 149, 215, 179, 147, 105, 24, 76, 79, 30, 180, 245, 226, 111, 184, 236, 160, 48, 220, 19, 179, 144, 7, 33, 31, 56, 202, 39, 192, 2, 17, 0, 0, 0, 1, 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