Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344f183e8ef161c6df593e14ddbc0d9adba2023dd569dcf305012b2706420db4

Tx prefix hash: 1c550578f8cdce2205cb6f4dd44ad6a91910d1ee10eb8e535d3d060e70c0d04f
Tx public key: 9a0709f6d6d88885d08e36a42b438922d0630663ab51789d512ae8635b083d4c
Timestamp: 1751334704 Timestamp [UCT]: 2025-07-01 01:51:44 Age [y:d:h:m:s]: 00:213:00:11:03
Block: 1316239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150350 RingCT/type: yes/0
Extra: 019a0709f6d6d88885d08e36a42b438922d0630663ab51789d512ae8635b083d4c021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08ee2931123967dc6579d1385ab4346ea3ddd0d550b0fdfc46f1702197191215 0.600000000000 1803898 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": 1316249, "vin": [ { "gen": { "height": 1316239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08ee2931123967dc6579d1385ab4346ea3ddd0d550b0fdfc46f1702197191215" } } ], "extra": [ 1, 154, 7, 9, 246, 214, 216, 136, 133, 208, 142, 54, 164, 43, 67, 137, 34, 208, 99, 6, 99, 171, 81, 120, 157, 81, 42, 232, 99, 91, 8, 61, 76, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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