Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 644f873ecd80447cebdab382026fb6f35f7c3b60f210851355f9db7bb59ce724

Tx prefix hash: 174f4fa20bc42e6dbf36757a85b36cca2d002cecc32371ec022206604ff8fa20
Tx public key: 4febf0e07978fb5ed7d554afca77ea561315f6671a6ee4f0d8f8a14f5be35f04
Timestamp: 1762928081 Timestamp [UCT]: 2025-11-12 06:14:41 Age [y:d:h:m:s]: 00:016:00:11:41
Block: 1410321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11466 RingCT/type: yes/0
Extra: 014febf0e07978fb5ed7d554afca77ea561315f6671a6ee4f0d8f8a14f5be35f04021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0c76f14d1f1c2490d5a21717c2077cd75bedb9e3a16e1ac5f4713e7e4eb13ec 0.600000000000 1898772 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": 1410331, "vin": [ { "gen": { "height": 1410321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0c76f14d1f1c2490d5a21717c2077cd75bedb9e3a16e1ac5f4713e7e4eb13ec" } } ], "extra": [ 1, 79, 235, 240, 224, 121, 120, 251, 94, 215, 213, 84, 175, 202, 119, 234, 86, 19, 21, 246, 103, 26, 110, 228, 240, 216, 248, 161, 79, 91, 227, 95, 4, 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