Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b049aa1214aefc299f07e3c8feec4e5e13134fbdec2610b270837fa19e84d621

Tx prefix hash: 8de612fba5fb20235755c62032863cc34149ba2c32f230533a265a1231d4cd58
Tx public key: 30fa64caf3b3efa4eb861a43138f9b02cc40ca6af11fa9807469670d24c4fe1c
Timestamp: 1701469064 Timestamp [UCT]: 2023-12-01 22:17:44 Age [y:d:h:m:s]: 01:046:18:05:32
Block: 903915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294797 RingCT/type: yes/0
Extra: 0130fa64caf3b3efa4eb861a43138f9b02cc40ca6af11fa9807469670d24c4fe1c02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.620803776000 dcy

stealth address amount amount idx
00: 2c10a36250338e06c55a4d86e096d8d9215869bf86b419c429fdf11b9d50c5c2 0.620803776000 1360614 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": 903925, "vin": [ { "gen": { "height": 903915 } } ], "vout": [ { "amount": 620803776, "target": { "key": "2c10a36250338e06c55a4d86e096d8d9215869bf86b419c429fdf11b9d50c5c2" } } ], "extra": [ 1, 48, 250, 100, 202, 243, 179, 239, 164, 235, 134, 26, 67, 19, 143, 155, 2, 204, 64, 202, 106, 241, 31, 169, 128, 116, 105, 103, 13, 36, 196, 254, 28, 2, 17, 0, 0, 0, 7, 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