Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7cdc7bc651c18382d62be101b61422aa70d3ce84fd939864ce6c2553966f4ae

Tx prefix hash: fb3f8c96984038c763d6f0889f99c6aef2784e116c1d1a39f960116482262de1
Tx public key: c049c2355b60a7157aab9dc4952f3fac738c3552a225de0ee4d5530b5741f1cb
Timestamp: 1726148750 Timestamp [UCT]: 2024-09-12 13:45:50 Age [y:d:h:m:s]: 00:101:04:50:46
Block: 1108525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72408 RingCT/type: yes/0
Extra: 01c049c2355b60a7157aab9dc4952f3fac738c3552a225de0ee4d5530b5741f1cb02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd83b2337719a2ea0446f7f9dd0e2a49eeb4313f7b4c2a56f148be47499cd68f 0.600000000000 1586450 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": 1108535, "vin": [ { "gen": { "height": 1108525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd83b2337719a2ea0446f7f9dd0e2a49eeb4313f7b4c2a56f148be47499cd68f" } } ], "extra": [ 1, 192, 73, 194, 53, 91, 96, 167, 21, 122, 171, 157, 196, 149, 47, 63, 172, 115, 140, 53, 82, 162, 37, 222, 14, 228, 213, 83, 11, 87, 65, 241, 203, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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