Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2583fa11b514b9665adff270543576fa236c5e6b1bac131d31be795ad863f2

Tx prefix hash: 76d8505c1d7d9db3d7c966064e6f49a5f28cd27e0f1b22cec07e6c06716f2a92
Tx public key: 80ff13ec6944dc22b8a63078ccf83e19e06febead681a449b6ab3beb80b85803
Timestamp: 1752642402 Timestamp [UCT]: 2025-07-16 05:06:42 Age [y:d:h:m:s]: 00:176:06:50:59
Block: 1326496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124821 RingCT/type: yes/0
Extra: 0180ff13ec6944dc22b8a63078ccf83e19e06febead681a449b6ab3beb80b8580302110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad8be378f992532f0c57c60c638a75e66a9a9c4ecee35af93c3776ad4de5a1ea 0.600000000000 1814247 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": 1326506, "vin": [ { "gen": { "height": 1326496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad8be378f992532f0c57c60c638a75e66a9a9c4ecee35af93c3776ad4de5a1ea" } } ], "extra": [ 1, 128, 255, 19, 236, 105, 68, 220, 34, 184, 166, 48, 120, 204, 248, 62, 25, 224, 111, 235, 234, 214, 129, 164, 73, 182, 171, 59, 235, 128, 184, 88, 3, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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