Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ab2b0e1c2736dd8b7689ca51553c913e82989a58a1e8bf6ca93f129aa87de5

Tx prefix hash: 97dad938dcc431e71942c42a9231d2471c622b19de06a2519e6c5e6a3d0cb714
Tx public key: 9ff26689f3dbd67f14ca8f0b8f4ace0f878e2824ee3da5c7c66d7565ef4b0fa0
Timestamp: 1760917479 Timestamp [UCT]: 2025-10-19 23:44:39 Age [y:d:h:m:s]: 00:078:19:48:11
Block: 1393680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56424 RingCT/type: yes/0
Extra: 019ff26689f3dbd67f14ca8f0b8f4ace0f878e2824ee3da5c7c66d7565ef4b0fa00211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c604e6d940f87ceaa3d5299760f7461486eea436b269f7351723cf056f64b7b8 0.600000000000 1881945 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": 1393690, "vin": [ { "gen": { "height": 1393680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c604e6d940f87ceaa3d5299760f7461486eea436b269f7351723cf056f64b7b8" } } ], "extra": [ 1, 159, 242, 102, 137, 243, 219, 214, 127, 20, 202, 143, 11, 143, 74, 206, 15, 135, 142, 40, 36, 238, 61, 165, 199, 198, 109, 117, 101, 239, 75, 15, 160, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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