Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56d83be73b88d66d5b3e3ed14de1c05e87c8b825c4cbeb56d09ef5f90502d7eb

Tx prefix hash: 4074d875f1f318babc1fc68834a1a7246c6e042cdab8bdf499deb6afc43a6cb3
Tx public key: 8442e9f6ab6f1b188206c53a6f254d14d2d6c254a096b09a682d8a46c0ff9391
Timestamp: 1712736401 Timestamp [UCT]: 2024-04-10 08:06:41 Age [y:d:h:m:s]: 00:320:22:24:45
Block: 997316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229430 RingCT/type: yes/0
Extra: 018442e9f6ab6f1b188206c53a6f254d14d2d6c254a096b09a682d8a46c0ff9391021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc139ddd597b7d517b14dea12adc91ff0a4785a9a4d158bcd787bc3ffab6567f 0.600000000000 1457746 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": 997326, "vin": [ { "gen": { "height": 997316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc139ddd597b7d517b14dea12adc91ff0a4785a9a4d158bcd787bc3ffab6567f" } } ], "extra": [ 1, 132, 66, 233, 246, 171, 111, 27, 24, 130, 6, 197, 58, 111, 37, 77, 20, 210, 214, 194, 84, 160, 150, 176, 154, 104, 45, 138, 70, 192, 255, 147, 145, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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