Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a894555561ed27fe650d0bc38e87ed8f41771c40aa4f94e8ae233d73ec022d12

Tx prefix hash: ef3033aa46c304cca2cc1d560fd39ba91b8dd05aeadc5fb5eb681a3f794563da
Tx public key: be50830b5e3272add251e54d994dec4a9f0b9a9ae37ee901e57bb6295049da4a
Timestamp: 1731648964 Timestamp [UCT]: 2024-11-15 05:36:04 Age [y:d:h:m:s]: 00:051:01:03:00
Block: 1154033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36535 RingCT/type: yes/0
Extra: 01be50830b5e3272add251e54d994dec4a9f0b9a9ae37ee901e57bb6295049da4a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8263d3cad9e6b07fb00966a3cb3c27319b9b203c837805f847f35f34b63cf63 0.600000000000 1639644 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": 1154043, "vin": [ { "gen": { "height": 1154033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8263d3cad9e6b07fb00966a3cb3c27319b9b203c837805f847f35f34b63cf63" } } ], "extra": [ 1, 190, 80, 131, 11, 94, 50, 114, 173, 210, 81, 229, 77, 153, 77, 236, 74, 159, 11, 154, 154, 227, 126, 233, 1, 229, 123, 182, 41, 80, 73, 218, 74, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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