Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aae36269c4deec5d4caf5a10da5e1c3b33d64e57b2fbde989724ed52d4b2cb9b

Tx prefix hash: b861ed1682570084f7bac6cc0b92382ad55843c19da1f875433ec6fb3f346353
Tx public key: 62238bc732ba60c00ea98d8b6288b8d804fa3d9e1fa6b7e24d3f14aca631716c
Timestamp: 1699348308 Timestamp [UCT]: 2023-11-07 09:11:48 Age [y:d:h:m:s]: 01:143:09:27:06
Block: 886345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363673 RingCT/type: yes/0
Extra: 0162238bc732ba60c00ea98d8b6288b8d804fa3d9e1fa6b7e24d3f14aca631716c02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.709857343000 dcy

stealth address amount amount idx
00: 5280838a04834e786a92e98fc51cf41d87a96226f7b63f7c0db600be24122f12 0.709857343000 1342160 of 0

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": 886355, "vin": [ { "gen": { "height": 886345 } } ], "vout": [ { "amount": 709857343, "target": { "key": "5280838a04834e786a92e98fc51cf41d87a96226f7b63f7c0db600be24122f12" } } ], "extra": [ 1, 98, 35, 139, 199, 50, 186, 96, 192, 14, 169, 141, 139, 98, 136, 184, 216, 4, 250, 61, 158, 31, 166, 183, 226, 77, 63, 20, 172, 166, 49, 113, 108, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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