Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b906ccba8ff919992b2bc3bc57c51da82a940c256006f687c50bf69bc0eae0cf

Tx prefix hash: 91d6db1111c74b6d718898be2fb3a4ea1f278334e878ad090d95f72f09b6d0d4
Tx public key: a3545e71218b1cb1e405450e3ee924a2f35663b0101c6735ce4b22f8a314fda6
Timestamp: 1765372431 Timestamp [UCT]: 2025-12-10 13:13:51 Age [y:d:h:m:s]: 00:029:19:08:38
Block: 1430580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21347 RingCT/type: yes/0
Extra: 01a3545e71218b1cb1e405450e3ee924a2f35663b0101c6735ce4b22f8a314fda602110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33a225920bda60384e3fe624d862981c27ff84e2c898d22be084b86d1849681d 0.600000000000 1919331 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": 1430590, "vin": [ { "gen": { "height": 1430580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33a225920bda60384e3fe624d862981c27ff84e2c898d22be084b86d1849681d" } } ], "extra": [ 1, 163, 84, 94, 113, 33, 139, 28, 177, 228, 5, 69, 14, 62, 233, 36, 162, 243, 86, 99, 176, 16, 28, 103, 53, 206, 75, 34, 248, 163, 20, 253, 166, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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