Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86143b416935cfa24c02aca6953f5f0481d570bb5c5534660325483da73560e1

Tx prefix hash: 35b4377d5b4adf6b9c42f5fa6c844ba76d68a994bd7c764833654789877e520d
Tx public key: 83c8edab6fb0a674df703b60f2aa8ab6cfc91e7625ef6221b30031506f0e17bb
Timestamp: 1715451364 Timestamp [UCT]: 2024-05-11 18:16:04 Age [y:d:h:m:s]: 00:132:18:16:48
Block: 1019869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95079 RingCT/type: yes/0
Extra: 0183c8edab6fb0a674df703b60f2aa8ab6cfc91e7625ef6221b30031506f0e17bb02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6581c8723536dcfae97db0e0a849567a0473ddd3eb12d75f6fecfde8bea20cc9 0.600000000000 1483922 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": 1019879, "vin": [ { "gen": { "height": 1019869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6581c8723536dcfae97db0e0a849567a0473ddd3eb12d75f6fecfde8bea20cc9" } } ], "extra": [ 1, 131, 200, 237, 171, 111, 176, 166, 116, 223, 112, 59, 96, 242, 170, 138, 182, 207, 201, 30, 118, 37, 239, 98, 33, 179, 0, 49, 80, 111, 14, 23, 187, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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