Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe1fa5e10ee43260d5d00cd3300e1eacac51df41b32026abf2887aea20509ac

Tx prefix hash: bc2e262984f7a3196d64439571e04f34c95eccc7d9eee50529eac1217eb0cc3b
Tx public key: 09debc3c484c9f25f04bd4bd38a2957a59b0a883941356767b905f0fc5970f3f
Timestamp: 1708259119 Timestamp [UCT]: 2024-02-18 12:25:19 Age [y:d:h:m:s]: 01:052:10:24:34
Block: 960219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298501 RingCT/type: yes/0
Extra: 0109debc3c484c9f25f04bd4bd38a2957a59b0a883941356767b905f0fc5970f3f0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ae62ea39566d74b84a99e9a4bf7070390a5102b3ace77784a5dd2d7adf8b5d6 0.600000000000 1419782 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": 960229, "vin": [ { "gen": { "height": 960219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ae62ea39566d74b84a99e9a4bf7070390a5102b3ace77784a5dd2d7adf8b5d6" } } ], "extra": [ 1, 9, 222, 188, 60, 72, 76, 159, 37, 240, 75, 212, 189, 56, 162, 149, 122, 89, 176, 168, 131, 148, 19, 86, 118, 123, 144, 95, 15, 197, 151, 15, 63, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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