Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf42774b100003278a1830a196276c1069cb09d07b9358a8625288d385b0b278

Tx prefix hash: caad288b7e0a9bf25ac8501f78f2f2a2880bd1f09e26384720c87cc3c6b7e67d
Tx public key: db928e084e1b364ac1bcab26cd2a8b97baafe2aeaf729796f8cb536c421f7071
Timestamp: 1751401291 Timestamp [UCT]: 2025-07-01 20:21:31 Age [y:d:h:m:s]: 00:139:02:41:37
Block: 1316766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97638 RingCT/type: yes/0
Extra: 01db928e084e1b364ac1bcab26cd2a8b97baafe2aeaf729796f8cb536c421f7071021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f66afd11ef6fcd9ddfc5160d7d4bf8b7bf2e4cdf108a65dd9500fe63f1e19a03 0.600000000000 1804429 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": 1316776, "vin": [ { "gen": { "height": 1316766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f66afd11ef6fcd9ddfc5160d7d4bf8b7bf2e4cdf108a65dd9500fe63f1e19a03" } } ], "extra": [ 1, 219, 146, 142, 8, 78, 27, 54, 74, 193, 188, 171, 38, 205, 42, 139, 151, 186, 175, 226, 174, 175, 114, 151, 150, 248, 203, 83, 108, 66, 31, 112, 113, 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