Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a098a88fa15257b2934d55c11170d1eb0282227e2e215ddce7ffd83c96d5d68b

Tx prefix hash: 4cffcd9e7ad0992261c33a2d657c673cfe6baa18bfe022b4c28dddc6bd6c0562
Tx public key: b51f38f82286f3c5058e17d200528a96503b0de3a3485db44edaa39b13f3da02
Timestamp: 1745125711 Timestamp [UCT]: 2025-04-20 05:08:31 Age [y:d:h:m:s]: 00:166:13:45:44
Block: 1265339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116718 RingCT/type: yes/0
Extra: 01b51f38f82286f3c5058e17d200528a96503b0de3a3485db44edaa39b13f3da020211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7f2d5a3121f4d8ffa41cc1c6c01df708c93ecb98319dda40546137c40ff39b7 0.600000000000 1752546 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": 1265349, "vin": [ { "gen": { "height": 1265339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7f2d5a3121f4d8ffa41cc1c6c01df708c93ecb98319dda40546137c40ff39b7" } } ], "extra": [ 1, 181, 31, 56, 248, 34, 134, 243, 197, 5, 142, 23, 210, 0, 82, 138, 150, 80, 59, 13, 227, 163, 72, 93, 180, 78, 218, 163, 155, 19, 243, 218, 2, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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