Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24413cb047956e6204d6322f40f5ecc61d6072bd981e8c3d5cd65e15ce1ae97d

Tx prefix hash: db681ed26d3e9ed1612ae73384414fdce2f12e894b24dec5e9665dba45b6a6cd
Tx public key: 60554e594f6ca21c747d6ebfc7d79e68cccac9fa0871f8bdda1602f93a1c8939
Timestamp: 1747342973 Timestamp [UCT]: 2025-05-15 21:02:53 Age [y:d:h:m:s]: 00:145:08:03:25
Block: 1283706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101512 RingCT/type: yes/0
Extra: 0160554e594f6ca21c747d6ebfc7d79e68cccac9fa0871f8bdda1602f93a1c89390211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56c9ee86a765dd53740d0c93ad30d9f18022afc7fd33ae8ba46b021daf6d4c9d 0.600000000000 1771125 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": 1283716, "vin": [ { "gen": { "height": 1283706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56c9ee86a765dd53740d0c93ad30d9f18022afc7fd33ae8ba46b021daf6d4c9d" } } ], "extra": [ 1, 96, 85, 78, 89, 79, 108, 162, 28, 116, 125, 110, 191, 199, 215, 158, 104, 204, 202, 201, 250, 8, 113, 248, 189, 218, 22, 2, 249, 58, 28, 137, 57, 2, 17, 0, 0, 0, 1, 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