Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b281560d2a63c735c56c31c7ab5f6c22dee02862000241e883c8450649bfb45

Tx prefix hash: cbddd7469c60a7cd699755986650cb4b4fddc5a3f19a7b4727e07b51d86cec8a
Tx public key: f91d65751b654db4995be759eb2e6c859d14d23e1fe66107b8d9a27283560a47
Timestamp: 1758969238 Timestamp [UCT]: 2025-09-27 10:33:58 Age [y:d:h:m:s]: 00:044:18:09:56
Block: 1377510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32049 RingCT/type: yes/0
Extra: 01f91d65751b654db4995be759eb2e6c859d14d23e1fe66107b8d9a27283560a4702110000000397baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e8be740306dde48f1d072d3c0faff01e4583d8c55897361eecd615b2ae6d70 0.600000000000 1865605 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": 1377520, "vin": [ { "gen": { "height": 1377510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e8be740306dde48f1d072d3c0faff01e4583d8c55897361eecd615b2ae6d70" } } ], "extra": [ 1, 249, 29, 101, 117, 27, 101, 77, 180, 153, 91, 231, 89, 235, 46, 108, 133, 157, 20, 210, 62, 31, 230, 97, 7, 184, 217, 162, 114, 131, 86, 10, 71, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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