Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fc8a47af6870c3502a415f2c19654eefe457a4d0caf66d1f76a705c19300926

Tx prefix hash: 66968cb143481634292ccb90af0eb52222815b46cc5998a494eb3764ad9bcb96
Tx public key: 92923293a84a150eefdc3b7da9be5b4f653e25164a3cfaa049fd6ae9cb0f46e5
Timestamp: 1707054307 Timestamp [UCT]: 2024-02-04 13:45:07 Age [y:d:h:m:s]: 01:047:11:00:00
Block: 950218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294971 RingCT/type: yes/0
Extra: 0192923293a84a150eefdc3b7da9be5b4f653e25164a3cfaa049fd6ae9cb0f46e50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38b706bc350e0fe1894f7af15fe6b267e126861ae9027aeee4ff2c86ff04bc9a 0.600000000000 1408800 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": 950228, "vin": [ { "gen": { "height": 950218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38b706bc350e0fe1894f7af15fe6b267e126861ae9027aeee4ff2c86ff04bc9a" } } ], "extra": [ 1, 146, 146, 50, 147, 168, 74, 21, 14, 239, 220, 59, 125, 169, 190, 91, 79, 101, 62, 37, 22, 74, 60, 250, 160, 73, 253, 106, 233, 203, 15, 70, 229, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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