Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b0a2fa957b92571206925b534b221f5aebf9080960f061c330ac3dfc3a3f547

Tx prefix hash: c91cf02b3b5ef19377e2169a4a463169f8be3f97bbe9a17390e9e4cb0fedd69f
Tx public key: f649cbfa4ec2c23d98c3ecc2d8e10e9bbf76fec4a721bcff5f1a36c9d6c81b41
Timestamp: 1759905672 Timestamp [UCT]: 2025-10-08 06:41:12 Age [y:d:h:m:s]: 00:076:17:36:09
Block: 1385270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54937 RingCT/type: yes/0
Extra: 01f649cbfa4ec2c23d98c3ecc2d8e10e9bbf76fec4a721bcff5f1a36c9d6c81b41021100000006a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b0576cd0cfc1a76b978969f5113f8d54d0c437017cadfee80c752e8692aa0a6 0.600000000000 1873429 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": 1385280, "vin": [ { "gen": { "height": 1385270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b0576cd0cfc1a76b978969f5113f8d54d0c437017cadfee80c752e8692aa0a6" } } ], "extra": [ 1, 246, 73, 203, 250, 78, 194, 194, 61, 152, 195, 236, 194, 216, 225, 14, 155, 191, 118, 254, 196, 167, 33, 188, 255, 95, 26, 54, 201, 214, 200, 27, 65, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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