Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4910455f1caa29047ca7cbd60b05f70fa471a98055c1e1e6b78cf629fadf00a

Tx prefix hash: 26133f6f26077d229b0c6164b9dae8b268ec2e084328fa5426b69451f60f391d
Tx public key: 7971253943b8c8b65e0fd7e8c5483c3da3eea7fccee01d68432dff990b157d33
Timestamp: 1755536565 Timestamp [UCT]: 2025-08-18 17:02:45 Age [y:d:h:m:s]: 00:094:04:47:33
Block: 1349315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67197 RingCT/type: yes/0
Extra: 017971253943b8c8b65e0fd7e8c5483c3da3eea7fccee01d68432dff990b157d330211000000078368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a08c6d9d65f4e0739e1cc50c966ac93f19c6d571053d86c52377e20d931e53b 0.600000000000 1837246 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": 1349325, "vin": [ { "gen": { "height": 1349315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a08c6d9d65f4e0739e1cc50c966ac93f19c6d571053d86c52377e20d931e53b" } } ], "extra": [ 1, 121, 113, 37, 57, 67, 184, 200, 182, 94, 15, 215, 232, 197, 72, 60, 61, 163, 238, 167, 252, 206, 224, 29, 104, 67, 45, 255, 153, 11, 21, 125, 51, 2, 17, 0, 0, 0, 7, 131, 104, 38, 109, 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