Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be83596598751d224c2be58be8c597a7d14d4c8bf72643a47aeb68b9aedeb4b

Tx prefix hash: a72cda034d0e55e0a9723efefd9be0d4f6248ccc39ea5f1f7b77218945aed51f
Tx public key: 0c30e8a7e790bd11dab0df1000a605c13cd5cb1063b1513435da42e224d7bad3
Timestamp: 1761847597 Timestamp [UCT]: 2025-10-30 18:06:37 Age [y:d:h:m:s]: 00:072:01:33:29
Block: 1401383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51604 RingCT/type: yes/0
Extra: 010c30e8a7e790bd11dab0df1000a605c13cd5cb1063b1513435da42e224d7bad302110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd238e44e974f63da7e0bd781c640de53d7718f6d744bbaa3adba3bdf2a03861 0.600000000000 1889702 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": 1401393, "vin": [ { "gen": { "height": 1401383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd238e44e974f63da7e0bd781c640de53d7718f6d744bbaa3adba3bdf2a03861" } } ], "extra": [ 1, 12, 48, 232, 167, 231, 144, 189, 17, 218, 176, 223, 16, 0, 166, 5, 193, 60, 213, 203, 16, 99, 177, 81, 52, 53, 218, 66, 226, 36, 215, 186, 211, 2, 17, 0, 0, 0, 2, 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