Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 300acd5cad387af164509f5faa59e3e08919b94ce37cfb2e7d00b5f5bd6ecb0b

Tx prefix hash: bef255d75f5d8022872e6d0f12afdfada4f7e2fd229b8e9a5feb6d9d08562e29
Tx public key: 6e9fe90a92b6893085336899b001805a5f766c8bc928f499e62338951d464f25
Timestamp: 1739253000 Timestamp [UCT]: 2025-02-11 05:50:00 Age [y:d:h:m:s]: 00:354:10:18:17
Block: 1216731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250992 RingCT/type: yes/0
Extra: 016e9fe90a92b6893085336899b001805a5f766c8bc928f499e62338951d464f250211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9da76913c169b45fc1b9f1fb4a8d00cf48e4afb141363ad3c1ca1d76e0859f15 0.600000000000 1703538 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": 1216741, "vin": [ { "gen": { "height": 1216731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9da76913c169b45fc1b9f1fb4a8d00cf48e4afb141363ad3c1ca1d76e0859f15" } } ], "extra": [ 1, 110, 159, 233, 10, 146, 182, 137, 48, 133, 51, 104, 153, 176, 1, 128, 90, 95, 118, 108, 139, 201, 40, 244, 153, 230, 35, 56, 149, 29, 70, 79, 37, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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