Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbfee01befbe68347d24c64d71915348cff6912f03ad0111b9b2092cf1e2ce5b

Tx prefix hash: dc97fc25d71175ff9d493a281660056449a6de4334f6645989216dfef0f1f9e1
Tx public key: d128a95c5ac73d246823dc7478a5f42e4c19b772f8c20889b6cf15f32616188d
Timestamp: 1707619564 Timestamp [UCT]: 2024-02-11 02:46:04 Age [y:d:h:m:s]: 01:055:06:24:30
Block: 954907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300546 RingCT/type: yes/0
Extra: 01d128a95c5ac73d246823dc7478a5f42e4c19b772f8c20889b6cf15f32616188d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 503a6e7b022341d502262bd78fc3ec3f7ae30e2c9a2ea55d208558868c7770af 0.600000000000 1414189 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": 954917, "vin": [ { "gen": { "height": 954907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "503a6e7b022341d502262bd78fc3ec3f7ae30e2c9a2ea55d208558868c7770af" } } ], "extra": [ 1, 209, 40, 169, 92, 90, 199, 61, 36, 104, 35, 220, 116, 120, 165, 244, 46, 76, 25, 183, 114, 248, 194, 8, 137, 182, 207, 21, 243, 38, 22, 24, 141, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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