Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e33cfc4f27361c56c3a9a3774e1984d392085c7740ce534ac2f0f0642107ea7

Tx prefix hash: be4dd7da3b2800cb54ea7eff9d075827e8a020d0c7f6acae45a25b4c8742268c
Tx public key: e7237d829cbb3eca4fd2c691685206f4f0bc52566d896c51dd58f80571963529
Timestamp: 1751701732 Timestamp [UCT]: 2025-07-05 07:48:52 Age [y:d:h:m:s]: 00:132:02:57:30
Block: 1319128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92765 RingCT/type: yes/0
Extra: 01e7237d829cbb3eca4fd2c691685206f4f0bc52566d896c51dd58f80571963529021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9b45bca745a06978ac5d0b9048b6a929ee901aae07ca2fe57332287a992607a 0.600000000000 1806817 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": 1319138, "vin": [ { "gen": { "height": 1319128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9b45bca745a06978ac5d0b9048b6a929ee901aae07ca2fe57332287a992607a" } } ], "extra": [ 1, 231, 35, 125, 130, 156, 187, 62, 202, 79, 210, 198, 145, 104, 82, 6, 244, 240, 188, 82, 86, 109, 137, 108, 81, 221, 88, 248, 5, 113, 150, 53, 41, 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