Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba20c89b01c4a6a3f5fad0d9782a12a811856792086970b3b2aacc7fa975cdce

Tx prefix hash: 6275a862b45bc9f0463e4bfa30eca4b8cab8622f89ac4ee3236f4bd3d0f4c094
Tx public key: 4496596d839ae698a1b535fe929393e8fd260b6026d21d94ec54d01a15f2c00f
Timestamp: 1736303126 Timestamp [UCT]: 2025-01-08 02:25:26 Age [y:d:h:m:s]: 00:157:08:02:50
Block: 1192581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112200 RingCT/type: yes/0
Extra: 014496596d839ae698a1b535fe929393e8fd260b6026d21d94ec54d01a15f2c00f021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce5dc0efb54b5a395d165b497e015c00abb916312c38dc701a768b08c64622cd 0.600000000000 1679136 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": 1192591, "vin": [ { "gen": { "height": 1192581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce5dc0efb54b5a395d165b497e015c00abb916312c38dc701a768b08c64622cd" } } ], "extra": [ 1, 68, 150, 89, 109, 131, 154, 230, 152, 161, 181, 53, 254, 146, 147, 147, 232, 253, 38, 11, 96, 38, 210, 29, 148, 236, 84, 208, 26, 21, 242, 192, 15, 2, 17, 0, 0, 0, 7, 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