Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5c04aefda55b612197a4ff1e6742e5a3c87a5f53dca8d13b8cf5b450af52ebb

Tx prefix hash: 2669df581fd36a59e26ca95fc6cfe3c0a43f1f926bb86b76ad20950728f3a280
Tx public key: 9f7aef6859d37a73aa3dc8b5c69a47cd98259109496151ced6ef42828fa8b3a6
Timestamp: 1703945380 Timestamp [UCT]: 2023-12-30 14:09:40 Age [y:d:h:m:s]: 01:317:05:47:40
Block: 924465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485554 RingCT/type: yes/0
Extra: 019f7aef6859d37a73aa3dc8b5c69a47cd98259109496151ced6ef42828fa8b3a602110000000aac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73f0d7adfaa93388dda2ec6649a2fead8133a3e65bbfbebe5693ff011fca691e 0.600000000000 1382215 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": 924475, "vin": [ { "gen": { "height": 924465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73f0d7adfaa93388dda2ec6649a2fead8133a3e65bbfbebe5693ff011fca691e" } } ], "extra": [ 1, 159, 122, 239, 104, 89, 211, 122, 115, 170, 61, 200, 181, 198, 154, 71, 205, 152, 37, 145, 9, 73, 97, 81, 206, 214, 239, 66, 130, 143, 168, 179, 166, 2, 17, 0, 0, 0, 10, 172, 50, 141, 17, 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